Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

2144

reference: 1-tree-1
name: 2144
tree-preservation-order: undefined
1-tpo-1
uprn
address-text
point: POINT (-0.932823 50.857035)
geometry: MULTIPOLYGON (((-0.932767 50.857029,-0.932769 50.857040,-0.932777 50.857050,-0.932789 50.857059,-0.932805 50.857064,-0.932823 50.857066,-0.932840 50.857064,-0.932856 50.857059,-0.932869 50.857051,-0.932877 50.857041,-0.932880 50.857030,-0.932878 50.857019,-0.932870 50.857009,-0.932858 50.857001,-0.932842 50.856996,-0.932824 50.856994,-0.932807 50.856995,-0.932791 50.857000,-0.932778 50.857008,-0.932770 50.857018,-0.932767 50.857029)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL